Well, the last beta roundup is here, and yes, it includes the new and improved ColdBox Dashboard. So please enjoy this beta as it includes the following updates and enhancements: - ColdBox Dashboard 2.0.0 - Welcome to ColdBox IoC Object Caching: You can now enable the IOC plugin to cache your service objects in the coldbox cache. In order to do this, you will have to enable it in your config file via the 'IOCObjectCaching' flag. Then, you will need to get rid of your singletons in your IOC declartion files and declare your singletons via the cfcomponet tag using the 'cache=true' metadata attribute. You can also assign a timeout here. - Caching Debugging Panel Enhanced. - Coldspring now receives the coldbox controller reference as part of the settings structure. The gap in the model is now closed. You can now reference the active coldbox controller in your IoC configuration files by using '${Setting: coldbox_controller not found}'. You will now be able to use the framework in your model objects if needed. - AppMapping setting in the config file is now optional. If set in the config file, then it will override the auto-detected mapping. This is a great feature if your main application root is not reachable from the url. - The new object to use in the event handler methods and layouts/views is 'Event' to standardize with conventions. - All documentation updated to 2.0.0 - BlueDragon fixes - Minor fixes,updates. - Install ANT task, so you can refactor the code if needed. - Application Template ANT task. You can now create new applications via ANT. - More guides coming soon. You can find the beta in the forums as usual Well, enjoy this latest beta as the release is coming soon.
Blog
Recent Entries
Your Development Team Is at Capacity. Here’s How to Keep Critical Work Moving!
The problem is not that your team lacks priorities.It is that maintenance, delivery, and long-term improvement are competing for the same people.
For companies running business-critical CFML, ColdFusion, or BoxLang applications, that pressure can be especially difficult to solve. Experienced developers are not always easy to hire quickly, application knowledge may be concentrated in one or two people, and a generalist may need significant context before taking ownership of the work. A permanent hire can also require a significant investment in recruiting, compensation, onboarding, and long-term capacity even when the immediate need is a specific project, urgent maintenance, or a period of transition.
Copy of BoxLang AI 3.4 Blog Series Part 5 : Reasoning Without the Guesswork
Reasoning-capable models have been usable in BoxLang AI for a while. params passes straight through to the provider body, so params: { thinking: { type: "enabled", budget_tokens: 10000 } } for Claude, or params: { reasoning_effort: "high" } for OpenAI, already reached the API. What never worked was reading the reasoning back. It was parsed out on arrival and silently dropped. In 3.4.0, that's fixed, and it's fixed the same way for every provider.
TestBox 7.1 Released : 47 New Ways to Assert, 29 of Them BoxLang-Only
TestBox 7.1.0 is here, and it is the largest single expansion of our assertion and expectation library since TestBox was born.
Add Your Comment
(2)
Mar 18, 2007 07:16:49 UTC
by Sana
Hi Luis,
Its really great work, Would you like to explain one thing. below text from your post:
[You will now be able to use the framework in your model objects if needed].
Thanks
Mar 18, 2007 12:06:31 UTC
by Luis Majano
Sure Sana,
I can actually send the coldbox controller reference into a bean declaration by using the following property in coldspring: ${coldbox_controller}
Once I receive the controller in the model objects I can use it and tap into the framework. Let's say I wanted a setting: coldbox_controller.getSetting()
Let's say I wanted to use the AOP logging tool: coldbox_controller.getPlugin().logEntry(,)>
Now, some people will say, then you tie your object model to a framework. Well, the answer is YES!! That is my purpose, to extend into the object model and take over.
There are so many good things about it, I am using it anyways. So If I ever decide to go to another framework, probably means, ColdBox is not around anymore.
So expect more object model infiltrations by coldbox.